-
Notifications
You must be signed in to change notification settings - Fork 324
Aria2 as advisory technique for 3.3.2 and 3.3.1 #4666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
change ARIA2 from sufficient for 3.3.1 to advisory add ARIA2 as an advisory for 3.3.2
Revised the language to make it clearer why this technique is advisory.
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
I don't get why, in the first line, "provide" has been replaced with "enhance": if a form field is visually identifiable as required (with an asterisk or whatever) and My understanding is also that, if the accessible name of the field contains some "required" wording, such as "First name (required)", then |
| <p>Use of <code>aria-required="true"</code> might be beneficial even when an asterisk or other text symbol is programmatically associated with the field as it may reinforce its <code>required</code> property for some assistive technology users.</p> | ||
| <p>The fact that the element is required is often visually presented (such as a sign or symbol after the control). Using the <code>aria-required</code> property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p> | ||
| <p>This technique is set as advisory for meeting 3.3.2 Labels or Instructions, because use of <code>aria-required="true"</code> alone, without any visual indicator, would not be perceivable to most users.</p> | ||
| <p>However, when an asterisk or other text symbol is associated with the field, using the <code>aria-required</code> property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <p>However, when an asterisk or other text symbol is associated with the field, using the <code>aria-required</code> property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p> | |
| <p>However, when an asterisk or other text symbol is associated with the field, using the <code>aria-required</code> property in addition to the visual presentation enables user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p> |
Closes #246